home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
IRIX Patches 1995 December
/
SGI IRIX Patches 1995 Dec.iso
/
relnotes
/
patchSG0000705
/
ch1.z
/
ch1
Wrap
Text File
|
1995-11-17
|
7KB
|
199 lines
- 1 -
1. _P_a_t_c_h__S_G_0_0_0_0_7_0_5__R_e_l_e_a_s_e__N_o_t_e
This release note describes patch SG0000705 to IRIX 5.3.
1.1 _S_u_p_p_o_r_t_e_d__H_a_r_d_w_a_r_e__P_l_a_t_f_o_r_m_s
This patch contains bug fixes for all hardware platforms
supporting IRIX 5.3. The software cannot be installed on
other configurations.
1.2 _S_u_p_p_o_r_t_e_d__S_o_f_t_w_a_r_e__P_l_a_t_f_o_r_m_s
This patch contains bug fixes for IRIX5.3. The software
cannot be installed on other configurations.
1.3 _B_u_g_s__F_i_x_e_d__b_y__P_a_t_c_h__S_G_0_0_0_0_7_0_5
Bug numbers from Silicon Graphics bug tracking system are
included for reference.
+o The TextField widget has an optional ModifyVerify
callback. A core dump can occur when a multi-character
locale such as Japanese is used. A SetValues call into
the TextField widget from a parent container such as
the FileSelectionBox or from an application will
trigger the core dump if there is a callback registered
on the ModifyVerify callback list. (Bug #291715)
1.4 _B_u_g_s__F_i_x_e_d__b_y__P_a_t_c_h__S_G_0_0_0_0_6_0_5
Patch705 also includes the bug fixes from patch605 of IRIX
5.3.
+o Recursive calls to XtSetValues (for instance, an
XtSetValues call nestled inside certain widget
callbacks which themselves call XtSetValues) can result
in a core dump. This patch adds code to prevent this
problem when XtSetValues is called recursively. (Bugs
#252275, 273570)
1.5 _B_u_g_s__F_i_x_e_d__b_y__P_a_t_c_h__S_G_0_0_0_0_2_5_8
Patch705 also includes the bug fixes from patch258 of IRIX
5.3.
+o The X Windowing System provides the user with the
ability to deal with color resources in different ways.
The user specifies a visual type when a window is
- 2 -
created. Windows of 8 bit PseudoColor and windows of 24
bit TrueColor can co-exist peacefully on the screen.
However, an X Error of Bad Match will occur if the
visual type, depth, and colormap resources do not form
a consistant set. In Motif, the depth and colormap of a
window are inherited from the widget parent whereas the
visual type is inherited from the window parent. A menu
or a dialog box usually has the root window as its
window parent but the button that launches it as its
widget parent. Since the button and the root window may
have been created using different visuals, this leads
to inconsistant sets of visual, depth, colormap tuples.
Many of the widgets in libSgm suffer this problem. This
patch fixes this problem by creating the menu or dialog
explicitly using the visual type of the shell that
contains the parent widget. Pixmaps are inflicted as
well and these are fixed for libSgm as well. (Bug
#255780)
+o Sliders in Scale widgets can appear in the wrong inital
position due to performance optimizations that were
added for the 5.3 release. The Scale is a container
widget which has a ScrollBar child. The ScrollBar is
not being properly initialized which results in the
Scale not getting the correct value. This patch fixes
this problem by allowing ScrollBar to calculate the
position of the slider while still keeping the
performance improvements. (Bug # 256130)
+o Programs that register non-text objects as Input
Methods can core dump in the 5.3 release due to
performance optimizations that were added to the
internationalization code. The code now properly checks
for the type of widget being used and accesses the
proper fields.
1.6 _S_u_b_s_y_s_t_e_m_s__I_n_c_l_u_d_e_d__i_n__P_a_t_c_h__S_G_0_0_0_0_7_0_5
This patch release includes these subsystems:
+o patchSG0000705.motif_eoe.sw.eoe
1.7 _I_n_s_t_a_l_l_a_t_i_o_n__I_n_s_t_r_u_c_t_i_o_n_s
Because you want to install patches for only the problems
you have encountered, patch software is not installed by
default. After reading the descriptions of the bugs fixed in
this patch, determine the patches that meet your specific
needs.
- 3 -
Patch software is installed like any other Silicon Graphics
software product. Follow the instructions in your _I_R_I_S
_S_o_f_t_w_a_r_e _I_n_s_t_a_l_l_a_t_i_o_n _G_u_i_d_e to bring up the miniroot form of
the software installation tools.
Follow these steps to select a patch for installation:
1. At the Inst>prompt, type
iiiinnnnssssttttaaaallllllll ppppaaaattttcccchhhhSSSSGGGG_x_x_x_x_x_x_x
where _x_x_x_x_x_x_x is the patch number.
2. Select the desired patches for installation.
3. Initiate the installation sequence. Type
IIIInnnnsssstttt>>>> ggggoooo
4. You may find that two patches have been marked as
incompatible. If this occurs, you must deselect one
of the patches.
IIIInnnnsssstttt>>>> kkkkeeeeeeeepppp ppppaaaattttcccchhhhSSSSGGGG_x_x_x_x_x_x_x
where _x_x_x_x_x_x_x is the patch number.
5. After completing the installation process, exit the
_i_n_s_t program by typing
IIIInnnnsssstttt>>>> qqqquuuuiiiitttt
To remove a patch, use the _v_e_r_s_i_o_n_s _r_e_m_o_v_e command as you
would for any other software subsystem. The removal process
reinstates the original version of software unless you have
specifically removed the patch history from your system.
vvvveeeerrrrssssiiiioooonnnnssss rrrreeeemmmmoooovvvveeee ppppaaaattttcccchhhhSSSSGGGG_x_x_x_x_x_x_x
where _x_x_x_x_x_x_x is the patch number.
To keep a patch but increase your disk space, use the
_v_e_r_s_i_o_n_s _r_e_m_o_v_e_h_i_s_t command to remove the patch history.
vvvveeeerrrrssssiiiioooonnnnssss rrrreeeemmmmoooovvvveeeehhhhiiiisssstttt ppppaaaattttcccchhhhSSSSGGGG_x_x_x_x_x_x_x
where _x_x_x_x_x_x_x is the patch number.